System and method for creating, managing, and displaying limited edition, serialized 3d digital collectibles with visual indicators of rarity classifications

ABSTRACT

A system and method for creating, managing, and displaying a limited edition, serialized 3D digital collectible, and rarity classifications of the collectibles and packs in which they are distributed. The 3D digital collectible may include at least one digital media file and associated data. A digital media file may relate to a visual representation of an event during an entertainment experience, such as a video highlight or related images, and the data may be data associated with the event, experience, and/or the digital media file.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/307,185, filed May 4, 2021, entitled “SYSTEM AND METHOD FOR CREATING,MANAGING, AND DISPLAYING LIMITED EDITION, SERIALIZED 3D DIGITALCOLLECTIBLES WITH VISUAL INDICATORS OF RARITY CLASSIFICATIONS”, which ishereby incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The field of the invention relates to a platform for creating, managing,and displaying limited edition, serialized 3D digital collectibles ofsports plays or other events, and rarity classifications of thecollectibles and/or packs in which they are distributed.

BACKGROUND OF THE INVENTION

Physical collectibles, such as baseball cards, are known. Recently,digital collectibles have also been developed. However, the technologyrelated to such digital collectibles is limited. For example, knowndigital collectibles are often static, two-dimensional, images. Theseand other technical limitations and drawbacks exist with knowncollectibles.

BRIEF SUMMARY OF THE INVENTION

According to an aspect of the invention, there is provided a system andmethod for creating, managing, and displaying a limited edition,serialized 3D digital collectible, and rarity classifications of thecollectibles and packs in which they are distributed. The 3D digitalcollectible may include at least one digital media file and associateddata or other content. A digital media file may relate to a visualrepresentation of an event during an entertainment experience, such as avideo highlight or related images, and the data may be data associatedwith the event, experience, and/or the digital media file.

A 3D digital collectible may be an instance of a limited edition set orbatch of instances of the same 3D digital collectible. The limitededition batch may include a predetermined number of instances of the 3Ddigital collectible in the batch, where the predetermined number may beguaranteed not to increase. Each instance of the limited editioncollectible in the batch may be marked at creation with a unique serialnumber. The serial number may be a unique number between 1-n, where n isthe predetermined number of instances of the 3D digital collectibles inthe batch. Each instance of the 3D digital collectible in the batch maybe displayed with an indication of the unique serial number for thatinstance of the 3D digital collectible and/or an indication of thenumber of collectibles in the batch. For example, the first instance ofthe 3D digital collectible in the batch may be associated with anindicator of 1 of n. The second instance of the 3D digital collectiblein the batch may be associated with an indicator of 2 of n and so on foreach of the n instances of the 3D digital collectibles in the batch. Thepredetermined number of instances may be stored for each 3D digitalcollectible as at least a part of rarity data that may be stored. Asdetailed below, the number of instances may be used in connection with ararity classification of the 3D collectible.

According to some embodiments, the platform may create different batchesof different limited edition 3D digital collectibles. Each of the setsmay have a predetermined number of instances of collectibles in the set.Based on a set of rules stored in the system (e.g., by a systemadministrator), each of the sets may be classified according to a raritytype based on the number of instances of the 3D digital collectible inthe batch. For example, there may be various classification descriptors(e.g., common, rare, legendary and/or other classification descriptors).By way of example, a common classification may correspond to batchesthat have more than a first number of instances (e.g., over 1000), arare classification may correspond to batches that have less than thefirst number of instances but more than a second number of instances,and a legendary classification may correspond to batches that have lessthan the second number of instances. Any number of classifications canbe used. The number of instances of a collectible in a batch thatdefines the classification can vary. This information may be stored foreach 3D digital collectible as rarity data.

According to some embodiments, a 3D digital collectible may be displayedwith a graphical visual indicator that corresponds to a rarityclassification type or otherwise indicates rarity data.

According to another aspect of the invention, different 3D digitalcollectibles from different batches may bundled into packs. Each packmay comprise only 3D digital collectibles of a single rarity typeclassification. In other cases, a pack may include 3D digitalcollectibles of a more than one rarity type classification. The packconfigurations may be determined by a system administrator.

According to some embodiments, a pack of 3D digital collectibles may bedisplayed with a graphical visual indicator that corresponds to a rarityclassification type or types of the 3D digital collectibles in the pack.

According to some embodiments, the system may include a set of rulesthat correlate to a special significance either across batches of 3Ddigital collectibles or within a particular batch. For example, thefirst instance in a batch (e.g., the #1 of n instances in the batch) maybe deemed to have a special significance. As another example, if thecollectible relates to a sports event depicting a highlight of anactivity by a particular player, a rule may correlate a specialsignificance within that particular batch for the instance of the batchthat has a serial number corresponding to a number of significance tothe player (e.g., the player's jersey number).

According to some embodiments, an instance of a 3D digital collectiblethat correlates to a special significance (e.g., based on a stored setof rules) may be displayed with a graphical visual indicator thatsignifies that instance has a special significance or a graphical visualindicator that signifies the specific special significance.

According to some embodiments, ownership of a limited edition 3D digitalcollectible may be represented by a non-fungible token (NFT), forexample an ERC-721 or other type of NFT. Each instance of the 3D digitalcollectibles in a batch may be represented by a separate NFT. Each NFTmay be minted with metadata that includes the instance of the 3D digitalcollectible (e.g., the unique serial number) in the batch and the totalnumber of instances of the 3D digital collectible in the batch. When theNFT is minted and/or assigned to a digital wallet of a purchaser of thecollectible, it may include metadata that includes the instance of the3D digital collectible (e.g., the unique serial number). Recording thisinformation on a blockchain (which is an immutable ledger) provides atechnological approach to enabling a collector to confirm whether theactual number of instances of the 3D digital collectible in the batchdoes not exceed the guaranteed number of instances of the 3D digitalcollectible that the issuer indicates the batch will not exceed. Thistechnological approach facilitates the guaranteed scarcity, confirmsownership of each instance and establishes the provenance of theinstance of each collectible.

According to another aspect of the invention, the 3D digital collectiblemay include at least one digital media file (e.g., a video file), or aset of digital media files, representing an event (e.g., a sports playor other events as detailed below) rendered on a representation of atleast a first of the n surfaces of the n-sided 3D shape, data or othercontent relating to the event rendered on at least a second surfacethereof, and other content on one or more other surfaces of the n-sided3D shape. Each surface may include a combination of digital media files,data and/or other content. The digital media file may be video clip ofthe event or a portion thereof that can be played automatically via amedia player associated with the display. A digital media file mayrelate to a visual representation of an event during an entertainmentexperience, such as a video highlight or related images, and the datamay be data associated with the event, experience, and/or the digitalmedia file. The digital media files, data and/or other content may bestored in a system memory associated with the server.

According to another aspect of the invention, the 3D digital collectiblemay include an overlay display element comprising an overlay surfacearranged to overlay one or more surfaces of the n-sided 3D shape. Theoverlay display element may include one or more surface(s) that arerendered to overlay one or more surfaces of the n-sided 3D shape to atleast partially overlay the one or more surfaces of the n-sided 3Dshape. The overlay display element may be rendered to appear as a glasslayer that at least partially overlays a surface of the n-sided 3Dshape. The overlay display layer may be rendered to appear as a glasslayer including at least a partially transparent planar display portionpositioned over at least a portion of one surface of the n-sided 3Dshape. The overlay display element may display digital media files dataor other content in the same manner as a surface of the n-sided 3Dshape. The overlay display element may also display an indication of therarity classification of the 3D digital collectible.

According to another aspect of the invention, the 3D digital collectiblemay include a surrounding structure display element arranged to surroundat least a portion of one or more surface of the n-sided 3D shape. Thesurrounding structure display element may include a framework arrangedaround at least one surface of the n-sided 3D shape. The surroundingstructure may include a framework forming at least part of a shape thatconforms to at least one surface of the n-sided 3D shape. Thesurrounding structure may include a framework forming at least part ofan n-sided 3D shape conforming to at least part of the n-sided 3D shapeof the 3D digital collectible. A framework may include visible markersor lines that at least partially define edges, lines, corners or shapesof the framework. The surrounding structure may display visualindicators based on stored rules and/or data relating to the digitalcollectible and/or the event rendered on a surface of the n-sided 3Dshape. The surrounding structure may display visual indicators of therarity classification of the 3D digital collectible.

According to another aspect of the invention, there is provided aplatform for creating, managing and displaying 3D digital collectiblesand rarity classifications thereof. The platform may include a computerserver including a processor programmed with computer instructionsincluding at least an administration module, a display generator, and amedia player. The platform may also include an associated computermemory that stores a data structure comprising media files, associateddata (including rarity data), and other content and an associationtherebetween, along with rules that define what digital media files,data and/or other content is to be displayed on the 3D digitalcollectible, including each of the surfaces thereof, what digital mediafiles, data and/or other content is to be displayed on the overlaydisplay element, what indications are to be displayed on the surroundingstructure, and metadata relating to events and other information.

According to some embodiments, the data structure stored in memoryincludes an association of the digital media files, data (includingrarity data) and/or other content that is to be displayed on a firstsurface of the n-sided 3D shape and the digital media files, data and/orother content that is to be displayed on the overlay display portion(e.g., when a first surface of the n-sided 3D shape is forward facing orat least partially forward facing). The data structure may include anassociation of the digital media files, data and/or other content thatis to be displayed on the overlay display element when the othersurfaces of the n-sided 3D shape are forward facing or at leastpartially forward facing.

According to some embodiments, the data structure stored in memoryincludes rules regarding an association of surrounding structure displayelements and visual indicators that are to be displayed to surround atleast part of the n-sided 3D shape based on one or more attributes ofthe digital collectible. By way of example, the surrounding structuremay display visual indicators of the rarity classification of the 3Ddigital collectible. The rules may specify the surrounding structuredisplay elements, their placement relative to the n-sided 3D shape, andthe visual indicators to be displayed in association with thesurrounding structure display elements. At least some of the visualindicators may be configured to indicate one or more attributes of thedigital collectible.

The system may also be configured by an administrative user to createrules for displaying the overlay display element(s), the surroundingstructure display elements, the visual indicators and what digital mediafiles, data (including rarity data), or content are to be displayedthereon based on various display parameters. The rules may include rulesthat specify when an overlay display element should be displayed, whereit should be displayed (e.g., which surface of the n-sided 3D shape itshould overlay), whether more than one overlay display element should bedisplayed, and rules regarding the digital media files, data and/orother content that is to be displayed on the overlay display element(e.g., glass) when the other surfaces of the n-sided 3D shape areforward facing or at least partially forward facing. Similarly, therules may include rules that specify when surrounding structure displayelements should be displayed, the configuration of the surroundingstructure display elements (e.g., what types of markers and/or lines areto be rendered), where they should be displayed (e.g., which surface(s)of the n-sided 3D shape it should surround), and rules regarding whatvisual indications should be provided on the surrounding structuredisplay elements. At least some of the rules may be dependent on whenparticular surfaces of the n-sided 3D shape are forward facing or atleast partially forward facing, one or more attributes of the digitalcollectible, a particular media file or other content associated withthe digital collectible and/or other criteria. The rules may be appliedto the digital media files, data and/or other content stored in theabove described data structure.

According to another aspect of the invention, the platform comprises adisplay generator for generating graphical user interfaces fordisplaying a representation of the 3D digital collectible and rarityclassifications thereof in accordance with the rules and a media playerfor playing the digital media files included with the 3D digitalcollectible based on scripted or user selected commands. The interfacemay be configured to display the 3D digital collectible and rarityclassifications thereof as a virtual, three dimensional n-sidedstructure discussed above.

According to another aspect of the invention, the platform comprises adisplay generator for generating graphical user interfaces fordisplaying a representation of the 3D digital collectible, including ann-sided 3D shape, overlay display element(s) arranged to overlay atleast portion(s) of a surface(s) of the n-sided 3D shape in accordancewith the rules, the surrounding structure display elements, the digitalmedia files, data (including rarity data) and/or other content that isto be displayed on one or more surfaces of the n-sided 3D shape, thedigital media files, data and/or other content that is to be displayedon the overlay display element(s) (e.g., glass) when a particular one ofthe surfaces of the n-sided 3D shape is forward facing or at leastpartially forward facing, and the visual indications that are to beprovided by the surrounding structure display elements. A media playermay be provided for playing the digital media files included with the 3Ddigital collectible based on scripted or user selected commands. Theinterface may be configured to display the 3D digital collectible withoverlays as a virtual, three dimensional n-sided structure discussedabove.

According to another aspect of the invention, based on a set of rulesand/or data, the display generator may be configured to depict arepresentation of a media file on at least one surface of the 3D digitalcollectible, including on an overlay display element (e.g., when arepresentation of a first surface of the 3D virtual display element isforward facing) and at least some of the data (including rarity data) orother content on another surface or surfaces of the 3D digitalcollectible, including an overlay display element, when that surface ofthe 3D digital collectible is forward facing. Forward facing may referto when a surface of the 3D virtual display element is displayed as userfacing when viewed from the perspective of a user, such that thesurface, or at least a portion thereof, is viewable by a user looking atthe display on which the 3D virtual display element is rendered.

According to another aspect of the invention, the 3D virtual displayelement representing the 3D digital collectible with overlay displayelement(s) and surrounding structure display elements may be dynamic,such that it is rotatable to display one or more of the surfaces and theassociated content (e.g., media file, data (including rarity data)and/or content) assigned to that surface (or overlay displayelement(s)). The 3D virtual display element may also allow the n-sided3D shape and the overlay display element(s) and surrounding structure tobe adjustable relative to each other.

According to another aspect of the invention, the interface may befurther configured such that when a surface of the 3D digitalcollectible depicting a representation of a media file is forwardfacing, a script or user command may cause the media player to play oneor more media files representing the event. The digital media files maycomprise a video clip of the event or multiple clips of the event fromdifferent perspectives. The multiple clips may be associated with thecollectible in a data structure stored in the memory. The multiple clipsmay be played sequentially (e.g., in accordance with a script) or theymay be stitched together in a specified order to create a single file.

According to another aspect of the invention, the event may include ahighlight from any type or category of experience, including withoutlimitation a sporting match. In the context of a sporting match, thehighlight may include a video clip of the highlight, such as a playerdunking a basketball or any other event from any type of sports match.The events are not limited to sports. The event may be video or otherform of capture of any of a number of other experiences, includingwithout limitation, sports, athletic events, esports and othercompetitions or other participatory experiences, artistic or theatricalproductions (such as a show, play, concert, opera or other production),an awards show, a television show, movie, game, streaming media, socialmedia or other entertainment experience, an information experience suchas a speech, news report, political debate or other informationexperience other categories of events or experiences. The platformdescribed is intended to cover a wide variety of event types from a widevariety of experiences.

According to another aspect of the invention, various types of mediafiles, data and other content may be associated and stored with theevent. A first type of data may include event data that describes theevent itself. In the context of a sporting match, the event data mayinclude the player, the type of action (e.g., a dunk, block, steal orother action), the date of the event, and other event data. A secondtype of data may include actor data relating to the person captured inthe event. For example, in the context of a sporting match, the actordata may include the player's age, hometown, college, statistics andother actor-related data. A third type of data may include context datathat describes additional information about the context of the event.For example, in connection with a sporting match, the context data mayinclude the teams that were playing when the event was captured, wherethe game was being played, the score of the game, and other contextdata). The media file, the various associated types of data and otheritems associated with an event may be collectively referred to ascontent. In some embodiments, the content is stored in memory inassociated with the event (or an event identifier) and at least some ofthe content may be selectively displayed on the 3D visual displayelement in accordance with a set of rules and/or metadata.

According to another aspect of the invention, the data associated withan event may also include metadata. Metadata may include informationspecified in connection with the creation of the digital collectiblethat specifies the content to be displayed and the manner in which thecontent should be displayed, such as what content should be displayed,where the content should be displayed (e.g., which surface), and how thedata should be displayed. Other metadata may include informationassociated with the classification of the digital collectible or otherinformation relating to the collectible, such as rarity data.

According to another aspect of the invention, the process of creating a3D digital collectible may include an administrative user interface forspecifying the rules for one or more 3D digital collectibles, includingthe n-sided 3D shape, any overlay display elements, any surroundingstructure display elements, any visual indicators, the a content to bedisplayed on the 3D digital collectible and the surfaces to which thedata is to be assigned, including surfaces of the n-sided 3D shape andoverlay display element(s) and other rules and input described herein todefine a 3D digital collectible, its various display options andattributes of thereof.

According to another aspect of the invention, the process of creating a3D digital collectible may include specifying the content to bedisplayed on the 3D digital collectible and the surfaces to which thedata is to be assigned.

The above stated aspects, as well as other aspects, features andadvantages of the invention will become clear to those skilled in theart upon review of the following description. It should be understoodthat the description and specific examples, while describing severalexemplary embodiments, are intended for purposes of illustration onlyand are not intended to limit the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or other aspects of the invention will be more apparent bydescribing in detail exemplary embodiments of the invention withreference to the accompanying drawings, in which:

FIGS. 1a-1f shows a 3D digital collectible according to some embodimentsof the invention;

FIGS. 2a-2q show aspects of a 3D digital collectible according to someembodiments of the invention;

FIGS. 3a and 3b show a digital media playing applications according tosome embodiments of the invention;

FIG. 4 shows aspects of a 3D digital collectible management systemaccording to some embodiments of the invention;

FIG. 5 shows aspects of a 3D digital collectible creation processaccording to some embodiments of the invention;

FIGS. 6a-6d show aspects of user controllable viewing tools according tosome embodiments of the invention;

FIG. 7 shows aspects of a pack of 3D digital collectibles according tosome embodiments of the invention; and

FIGS. 8a-8c show aspects of the display of contents of packs of 3Ddigital collectibles according to some embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Exemplary embodiments of the invention will now be described below byreference to the attached Figures. The described exemplary embodimentsare intended to assist the understanding of the invention and are notintended to limit the scope of the invention in any way. Like referencenumerals refer to like elements throughout. The examples are provided inconnection with a sports event by way of example only. The platform maybe used with other events including the other types of events referencedherein and other types of events.

The 3D Digital Collectible

Aspects of various types of events may include important portions whichcan be captured (as digital media files or other forms of capture). Suchdigital media files may include videos, images, sounds, and or otherforms of capture that record a particular event during an experience.For example, in relation to sports, an event can be a particular play,such as a dunk in a basketball game, a goal in a soccer match, or acatch in baseball. In such examples, the event may be captured as avideo, audio and/or other form of highlight, including from one or moreperspective views, as a digital media file or files. The event can be ofdifferent durations appropriate to memorialize the event. An event maybe part of a live-action experience, such as a sporting match or play,or a scripted or pre-recorded experience, such as a movie.

In an exemplary embodiment, a 3D digital collectible may be defined,generated, and rendered. The 3D digital collectible may include adigital media file (e.g., a video highlight clip) or a set of digitalmedia files (e.g., different perspectives of the same event or a seriesof files before, during and/or after the event) representing an event,along with data relating to the event, including scarcity data asexplained below. An event may include all or any identifiable portion ofan experience.

The 3D digital collectible may be a virtual, three dimensional n-sidedstructure (where n is preferably greater than 3), where the n-surfacesmay be configured to form an n-sided 3D shape, such as a cube, pyramid,octagon, or other 3D shape. One or more of the surfaces of the n-sidedshape may display one or more digital media files, or portions of suchdigital media files, and/or one or more portions of data (or othercontent) in a defined relationship stored in memory such that aparticular surface may display a digital media file or files, orportions thereof, a portion or portions of data, other content orcombinations thereof.

In the exemplary embodiment shown in FIG. 1 a, a 3D digital collectible100 includes a 6-sided 3D cube. In the perspective view of FIG. 1 a,first surface 110 and second surface 120 of the cube are visible. Firstsurface 110 has a digital media file 115, in this case a video clip.Second surface 120 has data 125, in this case the logo of the team ofwhich a player in digital media file 115 is a member. Additionally, 3Ddigital collectible 100 includes a cube shaped framework arranged aroundthe 3D cube, along with an overlay display element above first surface110, both of which are discussed in more detail below. FIGS. 1b-1e showfurther views of 3D digital collectible 100. In FIG. 1 b, anothersurface of 3D cube is shown. This surface includes data, in this case ateam logo and score related to the event to which the 3D collectible isrelated. In FIG. 1 c, another surface of 3D cube is shown. This surfacealso includes data, in this case a team logo and a date and descriptionof the event to which the 3D digital collectible is related. In FIG. 1d, another perspective view of 3D digital collectible 100 is shown. Inthis view, a surface 165 with different representation of a team logo isprovided, such that it appears within collectible 100, along with asurface 175 with a number of the player shown in the video clip onsurface 110. In this embodiment, the rear of surface 110 showing digitalmedia file 115 may be seen through 3D digital collectible 100. In FIG. 1e, another surface of the 3D cube with a team logo and copyright andsystem information is shown.

In various embodiments, the 3D digital collectible may be staticallydisplayed in its virtual environment (e.g. on a computer displayscreen), or may be dynamically displayed, such that it is rotatable todisplay one or more of the surfaces and the associated content (e.g., adigital media file and/or data) assigned to that surface. Such dynamicdisplay may be way of interactions with a user, in response to apredefined movement or movements (e.g., via a script or other computercode), or combinations thereof.

The digital media file may be any type of media, including still images,video, audio, and/or other media, or combinations of such media. Digitalmedia files may include a single view, audio track, or other recording,or composites of multiple views, audio tracks, or other recordings, suchas a composite video showing different perspectives of the event, suchas different camera views of a sports play or other event. The digitalmedia files may also include multiple views, audio tracks, or otherrecordings of the event from different perspectives, times, or durationsthat may be played sequentially and/or in other order. Such sequentialplay can be implemented by user interactions with a list of the multipleviews, audio tracks, or other recordings, by accessing the multipleviews, audio tracks, or other recordings in accordance with a script, orby stitching together the multiple views, audio tracks, or otherrecordings into a single digital media file. In this regard thecomposite or sequential digital media files may include different typesof files (e.g., they may include one or more of a video file, audiofile, or other recording). Portions of a single digital media file mayalso be identified, separated, and used as individual digital mediafiles in the manner described herein (e.g., a digital media file may besequentially divided with different portions considered as differentdigital media files). For example, a single digital media file may besequentially divided and provided on different surfaces of the 3Ddigital collectible.

The data relating to the event may include event data that describes theevent itself. Using a sporting match as an example, event data mayinclude such information as the player's name, the type of play (such asa dunk, block, or steal), the date and/or time of the event, and otherevent data. A second type of data may include actor data relating to theperson captured in the event. Again using a sporting match as anexample, actor data may include such information as the player'sstatistics, measurements, position, age, experience, hometown, college,draft selection, or other actor (or actors) data. A third type of datamay include context data that describes additional information about thecontext of the event. Again using a sporting match as an example,context data may include the teams that are playing, the location of thegame, the score of the game, the sports league, the sports season, andcontext data. The digital media file and any related data and/or othercontent may be collectively referred to as content.

Further exemplary embodiments of context data include informationrelated to an entertainment experience from which the event is drawn,situational information related to the entertainment experience, thesubject of the experience, and/or information related to the digitalmedia file. For example, context data related to a sporting match mayinclude the number of teams, the box score, game statistics, seasonalaverages for the player, media about the game, and other context data.In the sporting match example, the context data may relate to one ormore players or teams that are represented in a digital media file.

The various forms of data may be associated with a digital media file inany known manner, such as by tags, attributes, metadata, pointers and/orother associations. Data may be stored in a data structure in one ormore databases. The data structures may link an event with media files,data, content and metadata. The event and/or digital media file can besearched based on information associated with the event or the digitalmedia file.

Data may also include metadata. Metadata may include informationspecified in connection with the creation of the 3D digital collectiblethat specifies attributes of the digital collectible. The attributes mayinclude the configuration of the digital collectible (e.g. the number ofsides) the manner in which content should be displayed, such as whatcontent should be displayed, where the content should be displayed(e.g., on which surface of the n-shape), and how the content should bedisplayed, including in relation to other content. Other attributes ofthe digital collectible may be used.

The digital media file and data may also be created based on anotherdigital media file or data. For example, a digital media file includinga graphic and/or sound may be generated based on a digital media fileincluding a video. As such, 3D digital collectibles can include one ormore related digital media files and data. Further features of a 3Ddigital collectible are described in more detail in U.S. applicationSer. No. 17/229,455 titled “System And Method For Creating, Managing,And Displaying 3D Digital Collectibles” filed Apr. 13, 2021, herebyincorporated by reference in its entirety.

Rarity

Metadata may also include information associated with the uniqueness,rarity, or scarcity of the digital collectible in the system. Forexample, a 3D digital collectible may be a one of a kind instance of anevent, or there may be a predetermined number of instances of the event(e.g., copies of the 3D digital collectible). Other methods fordetermining the number of instances may be used. In any case, thedigital collectible may be identified by a serial number or other uniquevalue that uniquely identifies a particular 3D digital collectible inthe system, along with a unique identifier for the instance (e.g., 1 of1 or 1 of 10, etc.) as necessary. The unique identifier may be stored asrarity data by the system, as discussed below, and may be displayed onsurfaces or overlay display elements of the 3D digital collectible, oras information adjacent the 3D digital collectible when it is viewed.

In some embodiments, as shown in FIG. 1 f, a 3D digital collectible 180may be displayed with a tag 185 that displays event and context data 185a and rarity data 185 b. For example, 3D digital collectible 180 may bean instance of a limited edition batch of the same 3D digitalcollectible, as indicated by “LE” in displayed rarity data 185 b. Alimited edition batch may include a predetermined number of instances ofthe 3D digital collectible in the batch, where the predetermined numberis guaranteed not to rise, as indicated by the “50” in displayed raritydata 185 b. Each instance of the limited edition collectible in thebatch may be marked at creation with a unique serial number. The serialnumber may be a unique number between 1-n, where n is the predeterminednumber of instances of the 3D digital collectibles in the batch, asindicated by the “23” in displayed rarity data 185 b. Each instance ofthe 3D digital collectible in the batch may be displayed with anindication of the unique serial number for that instance of the 3Ddigital collectible and/or an indication of the number of collectiblesin the batch. For example, the first instance of the 3D digitalcollectible in the batch may be associated with an indicator of 1 of n.The second instance of the 3D digital collectible in the batch may beassociated with an indicator of 2 of n and so on for each of the ninstances of the 3D digital collectibles in the batch. In FIG. 1 f, thisis shown by the “23/50” in displayed rarity data 185 b. All of thisinformation may be stored for each 3D digital collectible as raritydata. Rarity information may also be displayed on any surface or overlaydisplay element of the 3D digital collectible instead of, or in additionto, a tag.

According to some embodiments, the platform may create different batchesof different predetermined numbers of different limited edition 3Ddigital collectibles. For example, one batch of a limited edition 3Ddigital collectible may have 50 copies, such as is shown in FIG. 1 f,while another batch of a different 3D digital collectible may have 1000copies. Based on a set of rules stored in the system (e.g., by a systemadministrator), such different batches with different predeterminednumbers of the 3D digital collectible may be classified according to ararity type based on the number of instances of the 3D digitalcollectible in the batch. For example, there may be variousclassification descriptors (e.g., common, rare, legendary and/or otherclassification descriptors). By way of example, a common classificationmay correspond to batches that have more than a first number ofinstances (e.g., over 1000), a rare classification may correspond tobatches that have less than the first number of instances but more thana second number of instances, and a legendary classification maycorrespond to batches that have less than the second number ofinstances. Any number of classifications or categorizations can be used.The number of instances of a collectible in a batch that defines theclassification can vary. This information may be stored for each 3Ddigital collectible as rarity data. Rarity values, categories, andrelated parameters can be set for an individual 3D digital collectibleas part of the initial creation process in defining the collectible.Rarity values, categories, and parameters may be selected by a creatorof the 3D digital collectible, or may be determined automatically basedon the selected digital media files and/or other data.

A rarity category for a particular 3D digital collectible may also bedisplayed on surfaces or overlay display elements of the 3D digitalcollectible, or as information adjacent the 3D digital collectible whenit is viewed. For example, FIG. 1f shows 3D digital collectible 180 withtag 185 showing rarity information 185 b with the rarity category“Legendary” displayed. Any categorical information may be displayed inthis manner. Rarity category information may also be displayed on anysurface or overlay display element of the 3D digital collectible insteadof, or in addition to, a tag. All of this information may be stored foreach 3D digital collectible as rarity data.

Alternatively or additionally, other displayed features of the 3Ddigital collectible may provide a visual indication of the raritycategory of the collectible, such as through colors, shading, material,textures, lighting and the like. For example, the cube-shapedsurrounding structure shown in FIG. 1f (discussed in more detail below)may include highlighted corners of a particular color that provide avisual indication that 3D digital collectible is a “legendary” 3Ddigital collectible.

According to some embodiments, the system may include a set of rulesthat correlate to a special significance either across batches of 3Ddigital collectibles or within a particular batch. For example, thefirst instance in a batch (e.g., the #1 of n instances in the batch) maybe deemed to have a special significance. As another example, if thecollectible relates to a sports event depicting a highlight of anactivity by a particular player, a rule may correlate a specialsignificance within that particular batch for the instance of the batchthat has a serial number corresponding to a number of significance tothe player (e.g., the player's jersey number). For example, in FIG. 1 f,the event is a dunk by Lebron James, whose jersey number is 23. Theserial number of the 3D digital collectible shown in FIG. 1f is #23/50.Thus, it may have special significance.

According to some embodiments, an instance of a 3D digital collectiblethat correlates to a special significance (e.g., based on a stored setof rules) may be displayed with a graphical visual indicator thatsignifies that instance has a special significance or a graphical visualindicator that signifies the specific special significance.

According to some embodiments, ownership of a limited edition 3D digitalcollectible may be represented by a non-fungible token (NFT), forexample an ERC-721 or other type of NFT. Each instance of the 3D digitalcollectibles in a batch may be represented by a separate NFT. Each NFTmay be minted with metadata that includes the instance of the 3D digitalcollectible (e.g., the unique serial number) in the batch and the totalnumber of instances of the 3D digital collectible in the batch. When theNFT is minted and/or assigned to a digital wallet of a purchaser of thecollectible, it may include metadata that includes the instance of the3D digital collectible (e.g., the unique serial number). Recording thisinformation on a blockchain (which is an immutable ledger) provides atechnological approach to enabling a collector to confirm whether theactual number of instances of the 3D digital collectible in the batchdoes not exceed the guaranteed number of instances of the 3D digitalcollectible that the issuer indicates the batch will not exceed. Thistechnological approach facilitates the guaranteed scarcity, confirmsownership of each instance and establishes the provenance of theinstance of each collectible.

System

A platform 400 for creating, managing, storing, rendering, anddisplaying 3D digital collectibles with overlay display element(s) andsurrounding structure according to an exemplary embodiment of theinvention is shown in FIG. 4. FIG. 4 shows system 410 with variousmodules and engines for defining, generating, and rendering a 3D digitalcollectible, system storage 430 for storing data, digital media files,3D collectibles, and collection information, and display 470 fordisplaying the 3D digital collectible to a user.

System 410 may include a computer server including a processor 412programmed with computer instructions including an administration module414, a display generator 416, a rendering engine 418, a gathering engine420, a collectible creation manager 422, a user account manager 424, auser control module 426, a collection manager 428, and a pack manager429. Platform 400 may also include a display 470 with 3D display 472 andmedia player 474. Platform 400 may also include an associated computermemory or system storage 430 that stores a data structure comprisingevent data 432, actor data 434, context data 436, metadata 438, digitalmedia files 440, 3D collectibles 442, rarity data 444, collection data446, pack data 448, associated data/content, and particularassociation(s) therebetween, including rules that define what is to bedisplayed on the surfaces, overlay display elements, and surroundingstructure of the 3D digital collectible. The components of the systemsmay be co-located or distributed.

Platform 400 may include tools to define and create a 3D digitalcollectible, including administration module 414 that manages and tracksownership of 3D digital collectibles by particular users, gatheringengine 420 that collects digital media files and data from event 450and/or other data sources, and collectible creation manager 422 thatcreates 3D digital collectibles and defines their data structures andrelationships. User account manager 424 is also provided to allow usersto create and manage accounts to interact with system 410, and usercontrol module 426 that provides various controls to users to performany of the steps herein.

As part of the process for creating a 3D digital collectible, gatheringengine 420 may gather digital media files 452 and data 454 related to anevent, either automatically or pursuant to a specific user request. Thisgathering may include obtaining necessary rights to the digital mediafiles 452 or data 454. Gathering engine 420 may then store collecteddigital media files 452 in system storage 430 as stored digital mediafiles 440. Gathering engine 420 may also store data 454 in systemstorage 430 as event data 432, actor data 434, or context data 436, asappropriate. Gathering engine 420 may also gather and store event data432, actor data 434, and context data 436 from other sources related toevent 450, such as other databases or data services related to news,statistics, sports leagues, etc.

Collectible creation manager 422 may use the stored digital media files440 and data 432, 434, 436, 438, and 444 to create a 3D digitalcollectible and store it in system storage 430 as a stored 3D digitalcollectible 443. Each stored 3D digital collectible 440 may includerarity data 444, such as the serial number of the predetermined numberof copies of the 3D digital collectible in the batch as discussed above,which serves as a globally unique identifier and may be represented asan NFT. Collectible creation manager 422 provides functionality tospecify the type of 3D digital collectible (e.g., what n-sided 3D shapeis to be used), visual design attributes of the 3D digital collectible(e.g., colors, shading, material, textures, and/or lighting), whichdigital media file(s) 440 and data 432, 434, 436, and 438, 444 are to bedisplayed on the 3D digital collectible, how the digital media file(s)and data are to be displayed (e.g., what surfaces the content is to beassigned, how the content is to be shown, played, or listened to, anysequence of display, etc.), whether to provide overlay display elements,including their type, design, and arrangement, and what digital mediafiles, data, or other visual indications are to be displayed thereon(and in what manner), whether to provide surrounding structures,including their type, design, and arrangement, and what data or visualindications are to be displayed thereon (and in what manner), whether toprovide a data tag adjacent the 3D digital collectible as it isdisplayed, including what data to display thereon, a rarityclassification of the 3D digital collectible, obtained from rarity data444, and any other of the related elements discussed herein. Collectiblecreation manager 422 may provide a GUI for a user to create a 3D digitalcollectible and select each of the above parameters, or may operate in apartially or fully automatic manner. After each of the parameters aboveare selected, collectible creation manager 422 may establishassociations or links between the 3D digital collectible (such as byusing its unique identifier) and any applicable digital media file(s)440, data 432, 434, 436, 438, or 444, and any other applicable data ordesign elements, and creates a data structure in memory associatingthese elements. This data structure is associated with the 3D digitalcollectible being created and is stored as metadata 438 in systemstorage 430. In this manner, each 3D digital collectible created bycollectible creation manager 422 is unique based on the aspects of theembodiments described herein.

Collectible creation manager 422 may also track and store in metadata438 all relationships between event data 432, actor data 434, contextdata 436, rarity data 444, and digital media files 440 that have beenidentified with regard to any other 3D digital collectible or aredetermined to otherwise be related during collection (e.g., event datasuch as a play may be linked to context data such as the related sportsleague) such that smart options may be presented by collectible creationmanager 422 to a user during creation of the 3D digital collectible.

An exemplary 3D digital collectible creation process is illustrated inFIG. 5. The creator (e.g., an user with an account on system 410 astracked by user account manager 424) may employ any user interface(e.g., a GUI provided by collectible creation manager 424) or otherinput mechanisms to make the following selections and perform thefollowing data entry. In the first step 510, a user may indicate hisdesire to create a new 3D digital collectible in connection with anevent, either from preexisting media or as part of a live event. Aunique identifier for the 3D digital collectible may be selected orgenerated at this stage. In Step 520, one or more digital media filesrelated to the event (e.g., digital media files 440) may be selected andobtained, including obtaining any necessary rights to show, play, ordisplay the digital media file. In step 530, data, such as event data432, actor data 434, context data 436, or rarity data 444 (or other dataor content) may be identified, obtained, or entered and stored in a datastructure associated with the 3D digital collectible (e.g. as metadata438). At step 540, the creator may select visual characteristics of thedigital collectible, such as a cube or other n-sided 3D shape, anoverlay display element configuration, and a surrounding structureconfiguration, and store them in the data structure associated with the3D digital collectible (e.g. as metadata 438). In step 550, the creatormay select how the digital media files and/or data are displayed,including how the digital media files and data are displayed inrelationship to each other and the various formats and features of thedigital collectible discussed herein, and store them in the datastructure associated with the 3D digital collectible (e.g. as metadata438). Additionally, with regard to digital media files that includevideo clips, the creator may identify a picture that can be displayed onthe surface of the 3D digital collectible as a representation of thedigital media file. In various embodiments, the picture may be a frameof the video clip or any other picture the creator may select. Thecreator may also specify that different pictures appear with regard tothe digital media file in different situations, such as when the 3Ddigital collectible is in different orientations or after the digitalmedia file has been played once.

According to another aspect of the invention, rules can be created toset forth what digital media files and data is presented on the 3Ddigital collectible as part of the 3D digital collectible creationprocess, such as in steps 520, 530, and 540 in FIG. 5. For example, the3D digital collectible may be designed to present a media file on onesurface of the 3D digital collectible (e.g., when a representation of afirst surface of the 3D virtual display element is forward facing) andrelated data on another surface or surfaces of the 3D digitalcollectible when that surface of the 3D digital collectible is forwardfacing. As a concrete example of this functionality, for a sportingevent, a highlight video can be rendered on a first surface and a teamlogo can be rendered on an opposite surface.

Rules may be stored in metadata 438, and may be accessed by collectiblecreation manager 422 during creation of the 3D digital collectible topartially automate creation, such as by automatically populating data432, 434, 436, or 444 based on selection of a particular digital mediafile 440, using predefined relationships between these elements asdiscussed above. Rules may also enforce standardization of theappearance of 3D digital collectibles. For example, rules may definerelationships between and among particular digital media files and data,and between particular surfaces of a 3D digital collectible, such thatsurfaces of a 3D digital collectible may be automatically populated withdigital media files and data in any appropriate manner. Digital mediafiles and data may also be classified or categorized by rules. In thismanner, specific data (i.e. belonging to a specific classification)and/or digital media files may be rendered at specific surfaces of then-surfaces of the 3D virtual element and can depend on data values.

Platform 400 may also include tools to display 3D digital collectibles,such as display generator 416 and rendering engine 418 for generatinggraphical user interfaces (GUIs) for displaying a 3D digital collectiblefor display therein to a user via 3D display 472 on display 470. Forexample, the 3D digital collectible (e.g. the digital media file anddata) may be configured to be displayed as a 3D display element. Thedigital collectible can be represented as, or otherwise include, the 3Ddisplay element. The 3D display element can be in a virtual 3D graphicalinterface. The 3D display element can have n-surfaces which are combinedtogether into an n-sided 3D shape, (cube, sphere, pyramid, octagon,etc.), overlay display elements, and surrounding structure. Each face orside of the of the n-sided shape can display at least one of theaforementioned digital media and/or data types. Each face or side of then-sided shape can have associated digital media and/or context data of aspecific type (for example, belonging to a specific classification ofmedia, such as images, video, text, sound for playback, etc.). Theoverlay display elements can also display at least one of theaforementioned digital media and/or data types.

The display generator 416 and rendering engine 618 may generate a GUI ondisplay 470, the representation of the 3D digital collectible and amedia player for playing the digital media file(s) included with the 3Ddigital collectible based on scripted or user selected commands. Theinterface may be configured to display the 3D digital collectible as thevirtual, three dimensional n-sided structure discussed above. Thedisplay may be pre-rendered or rendered in real-time as it is beingdisplayed. The 3D digital collectible may be rendered and displayed inany orientation, such as the perspective and plan views of FIGS. 1a-1f ,may be stationary in one view, or may change orientation between views(e.g., rotate, translate, etc.) either automatically based on elapsedtime, in reaction to a user interaction (e.g., mouse click, scroll barmovement, or touch interface), or both.

When a surface of 3D digital collectible that includes a digital mediafile is facing a user, the digital media may be displayed on thatsurface (or on an overlay display element, as discussed below). Forexample, in FIG. 1 a, a digital media file 115 is visible on surface 110of the 3D cube. If the digital media file is a video and/or audio track,display of the surface containing that digital media file also allowsthe video or audio to play. For example, in FIG. 1 a, if the displayeddigital media file 115 is a video, it may play in the orientation shown.

In other embodiments, a separate media player may be generated in theGUI by display generator 416 and rendering engine 618 to play digitalmedia files and/or data from surfaces of the 3D digital collectible(and/or overlay display elements), such as in an window or pop-upadjacent to the 3D digital collectible. The media player may alsopartially or fully overlay the 3D digital collectible, hover over asurface of the 3D digital collectible, or simply replace the 3D digitalcollectible in the GUI. The media player may automatically launch andbegin playing when a surface of the 3D digital collectible with anappropriate digital media file is visible, or upon user command. Themedia player may be of any shape and orientation to play the media file.Additionally, the view of the media player can be changed by furtheruser interaction. For example, the media player may be maximized on theuser screen for easier viewing automatically or based on user command.Selectors may also be provided to perform other display changes, or tolaunch a separate viewer or application.

FIGS. 3A and 3B illustrate exemplary embodiments of media player 474.FIG. 3A provides the media player over the surface of the 3D digitalcollectible, while FIG. 3B shows the media player partially overlayingthe 3D digital collectible. In either of these embodiments, the 3Ddigital collectible and media player may be provided in the same window,or in separate windows or popups. In any of the embodiments discussedabove, the media player may be partially transparent such that portionsof the 3D digital collectible under the media player are still visible.In any of the embodiments herein, various playback features may also beimplemented to allow the user more control of the playback, such asplay, pause, rewind, and replay buttons. Such controls may be placed onthe surface where the digital media file is shown, on the media player,or may be arranged thereto or anywhere else in the GUI.

In the above embodiments, the GUI and/or the media player may beconfigured to play the digital media file upon a direct user request, orautomatically (e.g., according to timing or positioning of the 3Ddigital collectible). For example, the GUI may be configured such thatwhen a surface of the 3D digital collectible depicting a representationof a media file is forward facing, a script or user command may causethe media player to play one or more media files representing the event.As discussed above, the digital media files may comprise a video clip ofthe event or multiple clips of the event from different perspectives.The multiple clips may be associated with the collectible in a datastructure stored in the memory. The multiple clips may be playedsequentially (e.g., in accordance with a script) or they may be stitchedtogether in a specified order to create a single file.

According to another exemplary embodiment, the GUI may be an interactivedisplay. For example, in response to user input selections via thegraphical user interface different surfaces of the n-sided display maybe displayed. For example, as shown in FIGS. 6a -6 d, GUI 650 may beconfigured to include a first display portion 600 with a set of icons602, 604, 606, 608, 610, 612 and second display portion 620 that showsvarious views of a 3D digital collectible corresponding to the icons. Asshown in FIG. 6d , media player 660 may also be launched in seconddisplay portion 620. Features of an interactive display are described inmore detail in U.S. application Ser. No. 17/229,430 titled “System andMethod for Creating, Managing, and Displaying an Interactive Display for3D Digital Collectibles,” filed Apr. 13, 2021, hereby incorporated byreference in its entirety.

Managing a Collection of 3D Digital Collectibles

According to other aspects of various embodiments, a user may manage thedisplay of multiple digital collectables within their account throughcollection manager 428. For example, in some embodiments, the digitalcollectables may be stored online (e.g., under control of the system), auser may create one or more collections of digital collectables andshare a link or other identifier associated with the collection andother users may use the link or other identifier to view thecollection(s). Data related to the collection may be stored ascollection data 446. Collections are described in more detail U.S.application Ser. No. 17/229,430 titled “System and Method for Creating,Managing, and Displaying an Interactive Display for 3D DigitalCollectibles,” filed Apr. 13, 2021, hereby incorporated by reference inits entirety.

Overlays and Markers

FIGS. 2a-2q show further exemplary embodiments of 3D digitalcollectibles that include one or more of the features discussed above,along with various additional features.

In some embodiments, a 3D digital collectible may also includesurrounding structure display elements. Surrounding structure displayelements include a framework that at least partially surrounds then-sided 3D shape.

A framework may include visible markers or lines that at least partiallydefine edges or shapes of the framework at least partially surroundingthe underlying 3D digital collectible structure. The markers or linesmay be provided, or may be provided in various colors, shades, andopacities, to provide a visual indication of attributes of the 3Ddigital collectible and/or the content thereof. For example, aparticular marker shape and color may be utilized to indicate a rarityclassification or other attribute of the 3D digital collectible. Markerand line shapes, colors, and opacities may also represent any of theother data categories mentioned herein.

In FIG. 2a , an exemplary surrounding structure related to 3D digitalcollectible 200 c is shown. In this embodiment, the surroundingstructure is a set of eight markers 210 c. In FIG. 2b , the exemplarysurrounding structure of FIG. 2a is portrayed about a 3D cube shape 200d with surfaces 203 d including a first digital media file 205 d (e.g.video, image, and/or sound), and a second digital media file 207 d (e.g.video, image, and/or sound) displayed thereon. In FIG. 2b , seven of theeight markers 210 d remain visible. In exemplary embodiments, themarkers can be rendered in a color, brightness, opacity different fromthe 3D cube shape 200 d (or with any other visible distinction) toindicate something about the 3D digital collectible, such as the rarityclassification or other data discussed above.

In some embodiments, a 3D digital collectible may also include anoverlay display element, or glass. Glass may include at least partiallytransparent planar objects positioned over at least one surface of then-sided 3D shape. Other appropriate 3D shapes may also be used (e.g.,domes, pyramids, etc.) adjacent one or multiple surfaces of the n-sided3D shape. The glass may display digital media files, data or othercontent in the same manner discussed above regarding a surface of then-sided 3D shape. The glass may also display content that has a specificrelationship to the digital media file or other content on the surfaceof the n-sided 3D shape over which the glass is arranged. For example, aglass arranged above a surface of the n-sided 3D shape that displays adigital media file of an event (e.g., a video of a dunk) may displaydata related to the event (e.g., displaying the player's name overlayingthe video of the dunk). The glass itself, and the data or digital mediadisplayed thereon, may be of varying transparencies such that thedigital media file on the surface of the n-sided 3D shape is visiblethrough the glass and data. The content to be displayed on glass, andthe manner in which it is displayed, can be specified during thecreation process in the manner discussed above.

FIGS. 2c-2h show various embodiments of overlay display elements andsurrounding structure, including various configurations of framework andglass. In some embodiments, these different configurations may denotedifferent rarity classifications. In other embodiments, these differentconfigurations may denote other categorical differences, or simplydesign preferences.

FIG. 2c shows exemplary n-sided 3D shape 210 with glass 230 renderedsuch that it overlays at a first distance a first surface 226 of n-sided3D shape 210 with a digital media file 228 thereon. In this embodiment,no glass is rendered above second surface 222 of n-sided 3D shape 210,which displays data 224, in this case a logo relevant to the digitalmedia file 228. In other embodiments, multiple glasses can be rendered.As shown in FIG. 2c , glass 230 is rendered to be clear. Glass 230 maybe of any color or opacity as compared to surface 226 that permitsviewing of digital media file 228. In some embodiments, FIG. 2crepresents how a 3D digital collectible would be displayed when the 3Ddigital collectible has a first rarity classification. For example, FIG.2c may represent how a 3D digital collectible would be displayed wherethe rarity classification is as a least rare 3D digital collectible(e.g., a “common” 3D digital collectible).

As shown in FIG. 2c , glass 230 is rendered to display data including aname 232 of a player in digital media file 228 and an indication 234that digital media file is a video clip that may be played as describedherein. By rendering name 232 and indication 234 on glass 230, name 232and indication 234 appear to be floating over digital media file 228. Insome embodiments, the data displayed on glass 230 may be static. Inother embodiments, the data may be dynamically updated. For example,indication 234 may display a running time of the digital media file 228,or a time remaining of the digital media file being played as discussedherein. In this embodiment, glass 230 does not have any identifiableborders or edges. Glass 230 may include borders or edges of a differentcolor or opacity in other embodiments. In some embodiments, the datadisplayed on glass 230 may include a rarity value or classification(e.g., a textual or numeric indication), such as by displaying theinformation in tag 185 in FIG. 1 f. In some embodiments, the color ortransparency of glass 230 may also be adjusted to indicate a rarityvalue or classification.

FIG. 2d shows another embodiment of the 3D digital collectible shown inFIG. 2c , where overlay lines 236 a and 236 b are rendered in additionto glass 230 in the same plane. Lines 236 a and 236 b may be of the sameor different color and opacity as glass 230. In the embodiment of FIG.2d , lines 236 a and 236 b are opaque in comparison to overlay 230 foreasy visibility. When a non-planar glass is used, such as a dome orpyramid, lines can be rendered such that they appear to be part of anextension of the shape of the glass surface. In some embodiments, FIG.2d represents how a 3D digital collectible would be displayed when the3D digital collectible has a second rarity classification. For example,FIG. 2d represents how a 3D digital collectible would be displayed wherethe rarity classification is reflective of a second least scarce 3Ddigital collectible (e.g., a “rare” 3D digital collectible). A rarityvalue or classification may also be indicated by adjusting theappearance of glass 230 or lines 236 a, 236 b. For example, lines 236 a,236 b can be of a different color, highlights, reflectivity, or the likethan glass 230 or the underlying 3D digital collectible structure 210.

FIG. 2e shows another embodiment of the 3D digital collectible shown inFIG. 2c , where a framework, including markers 237 a, 237 b, 237 c, and237 d, is rendered in addition to glass 230 in the same plane. Markers237 a, 237 b, 237 c, and 237 d may be of the same or different color andopacity as glass 230. In the example of FIG. 2e , markers 237 a, 237 b,237 c, and 237 d are opaque in comparison to overlay 230 for easyvisibility. When a non-planar glass is used, such as a dome or pyramid,markers can be rendered such that they appear to be part of an extensionof the shape of the glass surface. In some embodiments, FIG. 2erepresents how a 3D digital collectible would be displayed when the 3Ddigital collectible has a third rarity classification. For example, FIG.2e represents another embodiment of how a 3D digital collectible wouldbe displayed where the rarity classification is reflective of a secondleast scarce 3D digital collectible (e.g., a “rare” 3D digitalcollectible). A rarity value or classification may also be indicated byadjusting the appearance of glass 230 or markers 237 a, 237 b, 237 c,and 237 d. For example, markers 237 a, 237 b, 237 c, and 237 d can be ofa different color, highlights, reflectivity, or the like than glass 230or the underlying 3D digital collectible structure 210.

FIG. 2f shows another embodiment of the 3D digital collectible shown inFIG. 2c , where a framework with markers (e.g., 238 a, 238 b, 238 c, and238 d) and lines (e.g., 238 e, 238 f, 238 g, and 238 h) is rendered in athree dimensional shape surrounding the n-sided 3D shape 210 inconjunction with glass 230. Markers (e.g., 238 a, 238 b, 238 c, and 238d) and lines (e.g., 238 e, 238 f, 238 g, and 238 h) may be of the sameor different color and opacity as overlay 230. The markers and lines mayalso be of different color, opacity, and thickness relative to eachother. In some embodiments, FIG. 2e represents how a 3D digitalcollectible would be displayed when the 3D digital collectible has afourth rarity classification. For example, FIG. 2f represents how a 3Ddigital collectible would be displayed where the rarity classificationis reflective of a third least scarce 3D digital collectible (e.g., a“legendary” 3D digital collectible). A rarity value or classificationmay also be indicated by adjusting the appearance of glass 230, markers(e.g., 238 a, 238 b, 238 c, and 238 d), or lines (e.g., 238 e, 238 f,238 g, and 238 h). For example, markers (e.g., 238 a, 238 b, 238 c, and238 d), or lines (e.g., 238 e, 238 f, 238 g, and 238 h) can be of adifferent color, highlights, reflectivity, or the like than glass 230 orthe underlying 3D digital collectible structure 210.

In some embodiments of 3D digital collectibles, one or more of thesurfaces of the n-sided 3D shape may be made transparent. FIG. 2g showssuch an embodiment of a 3D digital collectible with a transparentsurface. FIG. 2g shows exemplary n-sided 3D shape 210 a with glass 230rendered such that it overlays at a first distance a first surface 226 aof n-sided 3D shape 210 a with a digital media file 228 a thereon. Inthis embodiment, no glass is rendered above second surface 222 a ofn-sided 3D shape 210 a, which displays data 224 a, in this case a logorelevant to the digital media file 228 a. In other embodiments, multipleglasses can be rendered. As shown in FIG. 2g , surface 222 a istransparent such that the structure of n-sided 3D shape 210 a can beseen therethrough. Further, in this embodiment, further data may bedisplayed in the volumetric center of the n-sided 3D shape, such as data225 a. Because surface 222 a is transparent, data 225 a is visible.Glass 230 a may be of any color or opacity as compared to surface 226 athat permits viewing of digital media file 228 a. In some embodiments,FIG. 2g represents how a 3D digital collectible would be displayed whenthe 3D digital collectible has a fifth rarity classification. Forexample, FIG. 2g may represent how a 3D digital collectible would bedisplayed where the rarity classification is as second most rare 3Ddigital collectible (e.g., a “platinum ultimate” 3D digitalcollectible).

As shown in FIG. 2g , glass 230 a is rendered to display data includinga name 232 a of a player in digital media file 228 a and in indication234 a that digital media file is a video clip that may be played asdescribed herein. By rendering name 232 a and indication 234 a on glass230 a, name 232 a and indication 234 a appear to be floating overdigital media file 228 a. In some embodiments, the data displayed onglass 230 a may be static. In other embodiments, the data may bedynamically updated. For example, indication 234 a may display a runningtime of the digital media file 228 a, or a time remaining of the digitalmedia file is being played as discussed herein. Glass 230 a may includeborders or edges of a different color or opacity in other embodiments.In some embodiments, the data displayed on glass 230 may include ararity value or classification (e.g., a textual or numeric indication),such as by displaying the information in tag 185 in FIG. 1 f. In someembodiments, the color or transparency of glass 230 a may also beadjusted to indicate a rarity value or classification.

FIG. 2g further provides a framework with markers (e.g., 239 a, 239 b,239 c, and 239 d) and lines (e.g., 239 e, 239 f, 239 g, and 239 h)rendered in a three dimensional shape surrounding the n-sided 3D shapein conjunction with glass 230 a. Markers (e.g., 239 a, 239 b, 239 c, and239 d) and lines (e.g., 239 e, 239 f, 239 g, and 239 h) may be of thesame or different color and opacity as overlay 230. The markers andlines may also be of different color, opacity, and thickness relative toeach other.

As discussed above, in some embodiments of 3D digital collectibles, asurrounding structure may be arranged around an n-sided 3D shape with a3D shape different from that of the n-sided 3D shape. For example, inFIG. 2g , lines 239 i are arranged so as to form a pyramid over thebottom surface (in this view) of the n-sided 3D shape. Any otherappropriate shape may be provided by appropriate design of markers andedges.

In some embodiments, only selected surfaces of an n-sided 3D shape arerendered in conjunction with one or more of markers, lines, and glass toform an overall 3D shape. FIG. 2h shows such an embodiment of the a 3Ddigital collectible with only selected surfaces of the n-sided 3D shaperendered. FIG. 2h shows exemplary n-sided 3D shape 210 b with a glass230 b rendered such that it overlays at a first distance a first surface226 b of the n-sided 3D shape 210 b with a digital media file 228 bthereon. No other surface of n-sided 3D shape is rendered. As shown inFIG. 2h , because other surfaces are not rendered, data displayed in thevolumetric center of the 3D digital collectible, such as data 225 b, isvisible. Glass 230 b may be of any color or opacity as compared tosurface 226 b that permits viewing of digital media file 228 b. In someembodiments, FIG. 2h represents how a 3D digital collectible would bedisplayed when the 3D digital collectible has a sixth rarityclassification. For example, FIG. 2g may represent how a 3D digitalcollectible would be displayed where the rarity classification is as themost rare 3D digital collectible (e.g., a “genesis ultimate” 3D digitalcollectible).

As shown in FIG. 2h , glass 230 b is rendered to display data includinga name 232 b of a player in digital media file 228 b and an indication234 b that digital media file is a video clip that may be played asdescribed herein. By rendering name 232 b and indication 234 b on glass230 b, name 232 b and indication 234 b appear to be floating overdigital media file 228 b. In some embodiments, the data displayed onoverlay 230 b may be static. In other embodiments, the data may bedynamically updated. For example, indication 234 b may display a runningtime of the digital media file 228 b, or a time remaining of the digitalmedia file is being played as discussed herein. Glass 230 b may includeborders or edges of a different color or opacity in other embodiments.In some embodiments, the data displayed on glass 230 b may include ararity value or classification (e.g., a textual or numeric indication),such as by displaying the information in tag 185 in FIG. 1 f. In someembodiments, the color or transparency of glass 230 a may also beadjusted to indicate a rarity value or classification.

FIG. 2h further provides a framework with markers (e.g., 240 a, 240 b,240 c, and 240 d) rendered in a three dimensional shape surrounding then-sided 3D shape in conjunction with glass 230 b. The markers may be ofvarying shapes and sizes to represent to a viewing the outline of a 3Dshape. Lines may also be provided to portray the shape, but are omittedin this embodiment. Markers (and lines) may be of consistent orinconsistent shape and size. For example, in FIG. 2h , marker 210 b isof a different shape than markets 240 a and 240 b, which are of asimilar shape. Markers (and lines) may be of the same or different colorand opacity as overlay 230 b. The markers (and lines) may also be ofdifferent color, opacity, and thickness relative to each other.

FIG. 2i provides another example embodiment where surface 222 c ofn-sided 3D shape 210 c is not rendered such that data displayed in thevolumetric center of the 3D digital collectible, such as data 225 c, isvisible. Additionally, internal sides of particular surfaces of then-sided 3D shape 210 c may also be seen when a particular surface is notrendered, such as is shown in this embodiment. For example, internalside of surface 226 c showing digital media file 228 c may be seen.

In some embodiments, a user may adjust the orientation of the 3D digitalcollectible, either my direct manipulation (e.g., click and drag) in aGUI or by particular user interfaces, such as described elsewhereherein. In some embodiments, the overlay display element and/orsurrounding structure will remain fixed in relation to the n-sided 3Dshape e as its orientation is changed. In other embodiments, all orportions of the overlay display element and/or surrounding structure mayremain in place as the orientation of the n-sided 3D shape e is changed.In some embodiments, the orientation of the overlay display elementand/or surrounding structure may be changed while the orientation of then-sided 3D shape remains fixed. For example, a user may slide,translate, or rotate the overlay display element in relation to the 3Ddisplay element, or in conjunction with the 3D display element. In otherembodiments, the overlay display element and/or surrounding structureand n-sided 3D shape may both change orientation to result in differentrelationships therebetween.

FIGS. 2j-2m provide additional embodiments showing interactions betweenn-sided 3D shape 290 and overlay display element 292. For example, wherea glass is arranged adjacent a surface of the n-sided 3D shapedisplaying data, glass may display additional data, such as a score asshown in FIG. 2k . In another example, glass may display an eventdescription and date in conjunction with surface displaying data, suchas is shown in FIG. 2l . Glass may also be blank when arranged adjacentsurfaces, such as is shown in FIGS. 2j and 2m . In other embodiments anydata or digital media file may be displayed on glass when it is arrangedadjacent a surface of the n-sided 3D shape displaying any other data ordigital media file (or where the surface of the n-sided 3D shape is notrendered).

When the orientation of the 3D digital collectible is changed, or theorientation of the n-sided 3D shape and overlay display element and/orsurrounding structure relative to each other, the digital media file ordata shown in glass may change. For example, glass position may changerelative to n-sided 3D shape between FIGS. 2k and 2l , and the datadisplayed on glass will change.

In the above embodiments, the type(s) of overlay display element(s)and/or surrounding structure (e.g. attributes thereof, the surface ofthe n-shape that glass overlays, the type and/or number of markers orlines, etc.) can depend on the data associated with the 3D digitalcollectible, the event data, actor data, context data, rarity data,and/or metadata. For example, the configurations of the surroundingstructure may depend on and correspond to the rarity of the digitalcollectible.

FIGS. 2n, 2o, 2p, 2q , depict exemplary embodiments of digitalcollectibles with surrounding structure with various types of markersand lines. FIG. 2n shows digital collectible 200 j with digital mediafile 200 j and one or more bar-shaped lines 210 j. FIG. 2o shows digitalcollectible 200 k with digital media file 205 k and corner-shapedmarkers 210 k. FIG. 2p shows digital collectible 200 l with media 205 land markers 210 l. In this embodiment, only two markers are rendered.Any number of markers or lines may be rendered to serve the purposes ofthe framework described herein. Finally, FIG. 2q shows digitalcollectible 200 m with digital media file 205 m and triangular-shapedmarkers 210 m. Various additional shapes for markers may be used, aswell as various combinations thereof.

Packs

In an exemplary embodiment, 3D digital collectibles can be provided tousers (e.g., by sale or trade) in a digital pack, or set of different 3Ddigital collectibles. These packs may be digitally rendered on agraphical user interface in a manner similar to that of the 3D digitalcollectibles discussed above. The packs may be configured by a systemadministrator and in accordance with a set of rules and data parameters.

FIG. 7 depicts an exemplary embodiment of a pack 700, as it may bedisplayed on a GUI. The pack 700 may be rendered in any fashion thatwould represent a set of 3D digital collectibles to a user. In thisembodiment, pack 700 is rendered to resemble a physical pack of tradingcards. Pack 700 includes graphical data 705 or other data, includingevent, context and/or metadata 210 associated to the collectibles in thepack. For example, pack 700 can include representations of the dates ofthe events of its constituent digital collectibles, the actors in theevents, and the like. Pack 700 may also include an indication of thenumber of 3D digital collectibles contained therein. However, accordingto some embodiments, the individual items of the pack may not berevealed at this level of display.

Pack 200 may also include a rarity indication 210 that indicates therarity classification of one or more of the 3D digital collectiblescontained in the pack 200. In this embodiment, the rarity indication 210is “rare,” which indicates that at least one of the 3D digitalcollectibles of pack 200 is a “rare” 3D digital collectible. Othervisual indicators may be used to signify a rarity classification for thepack, such as colors, fonts, designs, holograms, and the like.

According to some embodiments, different 3D digital collectibles fromdifferent batches may bundled into packs. Each pack may comprise only 3Ddigital collectibles of a single rarity classification. In other cases,a pack may include 3D digital collectibles of a more than one rarityclassification. The pack configurations may be determined by a systemadministrator. Where the pack contains 3D digital collectibles of morethan one rarity classification, the system will apply rules to determinewhat rarity indication to display on the pack. For example, rarityindication may be set to indicate the most rare rarity classification ofany of the 3D digital collectibles in the pack (e.g., if at least one 3Ddigital collectible is “rare,” the indication 210 will be “rare.”), ararity classification of the majority of the 3D digital collectibles inthe pack, or any other desired configuration.

Pack 700 may also be rendered with one or more colors, shading,lighting, and/or textures. The colors, shading, material, textures,and/or lighting can correspond to values of the data, such as eventdata, context data, rarity data, and/or metadata for one or more digitalcollectibles within the pack 700. In exemplary embodiments, packs may berendered as shiny or holographic.

In some embodiments, a user seeking to acquire a pack 700 may not bepermitted to see the specific 3D digital collectibles that are part ofpack 700 before it is purchased. In other embodiments, some amount ofdata relating to the pack, such as event data, context data, raritydata, or metadata corresponding to the pack may be shared. For example,the rarity classification of a pack or at least one of the 3D digitalcollectibles of the pack may be indicated as discussed above (e.g.,ultimate, legendary, rare, or common).

In some embodiments, the pack can be visually represented asuser-manipulatable packaging icon (e.g. square, rectangular other shape)that can be digitally “opened.” For example, the pack can be “opened” byuser interactions, such as by clicking a button, virtually tearing thepack, or other appropriate manipulation.

A GUI may display a separate icon for each of the packs associated withthe user account. After acquisition and opening by a user, an iconrepresenting each of the 3D digital collectibles associated with thepack may be displayed in a grid, carousel, or other arrangement forviewing. The manner in which the 3D digital collectibles icons spreadout of the pack (i.e. a visual representation thereof) may depend on oneor more values of related data, such as event data, context data, ormetadata. The display may be similar to that of a collection asdescribed in more detail in U.S. Application filed May 3, 2021 as U.S.patent application Ser. No. 17/306,185, titled “System And Method ForCreating, Managing, And Displaying User Owned Collections Of 3D DigitalCollectibles,” hereby incorporated by reference in its entirety.

For example, in some embodiments, GUI 800 will display the 3D digitalcollectibles icons in pack 700 as shown in FIG. 8a . In this example,pack 700 includes three (or other number of) individual 3D digitalcollectibles. GUI 800 may display the individual 3D digital collectiblesicons of pack 700 in any manner. In the FIG. 83a embodiment, eachindividual 3D digital collectible icon is shown in a grid in aperspective view with a digital media file on one surface and data onthe second, but the 3D digital collectibles icon may be shown in anyorientation, including any of the orientations discussed above.Individual 3D digital collectibles icons may be arranged in a commonorientation, or different orientations. The individual 3D digitalcollectibles icons may also be arranged in a list or other arrangementthat allows a user to view the contents of pack 700.

According to an embodiment, a user may also select one of the 3D digitalcollectibles icons in pack 700 shown in FIG. 38. The GUI will thendisplay the selected 3D digital collectible and allow further userinteraction, or may launch an interactive GUI such as is described inmore detail in U.S. Application filed Apr. 13, 2021 as U.S. patentapplication Ser. No. 17/229,430, titled “System And Method For Creating,Managing, And Displaying An Interactive Display For 3D DigitalCollectibles,” hereby incorporated by reference in its entirety.

The 3D digital collectibles associated with the non-selected icons maynot be revealed until the user selects the corresponding icon. A userneed not open any pack immediately on purchase. Nor must a user selecteach of the icons of a pack within a single session. If a user selectsnone, one or more, but less than all of the icons in a pack, the 3Ddigital collectables associated with the non-selected icons will remainunrevealed to the user. However, these 3D digital collectables remainassociated with the user account. A GUI associated with the user accountprofile (and other displays) may display a visual indication of theuser's packs, and a visual indication of whether a pack has been openedor not. If a pack is not yet opened, one or more indicators may bepresented via a GUI to indicate that pack status. If a pack has beenopened, but not all of the 3D digital collectables of the pack have beenrevealed, one or more indicators may be presented via a GUI to indicatethat pack status. Other visual indicators may be displayed to indicatethe status of the packs and/or 3D digital collectables within a pack.

In some embodiments, media player 809 may automatically play the digitalmedia file in the selected 3D digital collectible. Before, during and/orafter the media player starts to play the digital media file, the systemmay display various data, metadata, context, scarcity indicator and/orother information or content relates to the selected digitalcollectable. This variety of media and data and the delayed reveal ofthe digital collectables creating an enjoyable and user experience andcan add suspense to the process.

According to another embodiment, a user may request that the digitalmedia files included in the 3D digital collectibles of pack 700 beplayed in a media player or separate window or pop-up. For example, auser may select the watch button 708 in the FIG. 8a embodiment, whichmay launch a media player in GUI 800, such as media player 809 in FIG.8b . Media player 809 is described in more detail in a U.S. PatentApplication filed Apr. 13, 2021 as U.S. application Ser. No. 17/229,455,titled “System And Method For Creating, Managing, And Displaying 3DDigital Collectibles,” hereby incorporated by reference in its entirety.

In an embodiment, media player 809 plays each of the digital media filesin the selected (opened) 3D digital collectibles of pack 700individually and/or in a continuous serial loop, either by sequentiallyplaying the individual digital media files or by stitching together theindividual digital media files into one file. In other embodiments, GUImay provide the user options to play particular digital media files,such as by showing individual links or icons, and may allow the user tocontrol the playback.

In another embodiment, after a user selects watch button 808 in FIG. 8a, GUI 800 may sequentially display 3D digital collectibles 805 a, 805 b,and 805 c and their respective digital media files. For example, GUI 800may display a first 3D digital collectible 805 a, automatically play adigital media file from the first 3D digital collectible 805 a, thendisplay a second 3D digital collectible 805 b and automatically play adigital media file from the second 3D digital collectible 805 b, and soon until each 3D digital collectible and digital media file has beendisplayed in pack 700.

In an embodiment, pack 700 may include a link creation button 807 for auser to create a link to pack 700 to allow other users to view thecontents of pack 700. Other buttons, links, or interfaces may beprovided.

In another embodiment, a pack 700 may itself include multiple packs of3D digital collectibles. In such an embodiment, packs, rather than 3Ddigital collectibles, may be displayed in GUI 800 in FIG. 8a , andanother GUI is rendered to display the 3D digital collectibles in thesub-packs. Packs containing sub-packs may be denoted by visual cues,such as shading, highlights, boxes surrounding the individual 3D digitalcollectibles of a sub-collection.

In another embodiment, the 3D digital collectibles of pack 700 may behidden after the initial opening of the pack 700, as shown in FIG. 8c .In this embodiment, GUI 810 includes icons (e.g., 805 a, 805 b, and 805c) that include an indication that clicking on the icon will reveal a 3Ddigital collectible that is included in the pack. In some embodiments,clicking on an icon will result in the display of the underlying 3Ddigital collectible, either by replacing the icon 815 a with a renderingof the 3D digital collectible (such as is shown in FIG. 8a bycollectible 805 a), or by making the 3D digital collectible morepronounced in a separate view.

In some embodiments, after an icon 815 a is selected and replaced by adigital collectible 805 a, digital collectible 805 a remains visible. Inthis manner, by selecting each icon 815 a, a view similar to that ofFIG. 8b can be provided, where each icon 815 a, b, and c is replaced by,for example, 3D digital collectibles 805 a, 805 b, and 805 c. Thecollectibles may then be interacted with in the manner described above.

In exemplary embodiments, system 410 may include pack manager 429 thatcreates and manages packs. Pack manager interfaces with rendering engine418 and display generator 416 to display the packs, intermediate GUI,and underlying 3D digital collectibles in the manner discussed above.Pack manager may assign a unique identifier to each pack. Data relatedto each pack may be stored as pack data 448. Such data includesrelationships between pack identifiers and constituent 3D digitalcollectibles.

Pack manager 429 may assign 3D digital collectibles to packs. In someembodiments, the 3D digital collectibles may be randomly assigned topacks. In other embodiments, the 3D digital collectibles may be assignedaccording to data, such as event data, context data, or metadata. Inother words, the 3D digital collectibles in a pack may havecorresponding context data. For example, in a sports context, the 3Ddigital collectibles in a pack may each correspond to live entertainmentevents of a specific league, team, player, moves type, and/or score.

Processing Devices and Processors

In some embodiments, the platforms, systems, media, and methodsdescribed herein, including system 400, include a processing devices,processors, or use of the same. In further embodiments, the processingdevice includes one or more hardware central processing units (CPUs) orgeneral purpose graphics processing units (GPUs) that carry out thedevice's functions. In still further embodiments, the processing devicefurther comprises an operating system configured to perform executableinstructions. In some embodiments, the processing device is optionallyconnected a computer network. In further embodiments, the processingdevice is optionally connected to the Internet such that it accesses theWorld Wide Web. In still further embodiments, the processing device isoptionally connected to a cloud computing infrastructure. In otherembodiments, the processing device is optionally connected to anintranet. In other embodiments, the processing device is optionallyconnected to a data storage device. In accordance with the descriptionherein, suitable processing devices include, by way of non-limitingexamples, cloud computing resources, server computers, server clusters,desktop computers, laptop computers, notebook computers, sub-notebookcomputers, netbook computers, netpad computers, handheld computers,mobile smartphones, and tablet computers. In some embodiments, theprocessing device includes an operating system configured to performexecutable instructions. The operating system is, for example, software,including programs and data, which manages the device's hardware andprovides services for execution of applications. Those of skill in theart will recognize that suitable server operating systems include, byway of nonlimiting examples, FreeBSD, OpenBSD, NetBSD®, Linux, Apple®Mac OS X Server®, Oracle® Solaris®, Windows Server®, and Novell®NetWare®. Those of skill in the art will recognize that suitablepersonal computer operating systems include, by way of non-limitingexamples, Microsoft® Windows®, Apple® Mac OS X®, UNIX®, and UNIX-likeoperating systems such as GNU/Linux®. In some embodiments, the operatingsystem is provided by cloud computing. Those of skill in the art willalso recognize that suitable mobile smartphone operating systemsinclude, by way of non-limiting examples, Nokia® Symbian® OS, Apple®iOS®, Research In Motion® BlackBerry OS®, Google® Android®, MicrosoftWindows Phone® OS, Microsoft Windows Mobile® OS, Linux®, and Palm®WebOS®. In some embodiments, the processing device includes a storageand/or memory device. The storage and/or memory device is one or morephysical apparatuses used to store data or programs on a temporary orpermanent basis. In some embodiments, the device is volatile memory andrequires power to maintain stored information. In some embodiments, thedevice is non-volatile memory and retains stored information when theprocessing device is not powered. In further embodiments, thenon-volatile memory comprises flash memory. In some embodiments, thenonvolatile memory comprises dynamic random-access memory (DRAM). Insome embodiments, the non-volatile memory comprises ferroelectric randomaccess memory (FRAM). In some embodiments, the non-volatile memorycomprises phase-change random access memory (PRAM). In otherembodiments, the device is a storage device including, by way ofnon-limiting examples, CD-ROMs, DVDs, flash memory devices, magneticdisk drives, magnetic tapes drives, optical disk drives, and cloudcomputing based storage. In further embodiments, the storage and/ormemory device is a combination of devices such as those disclosedherein. In some embodiments, the processing device includes a display tosend visual information to a user. In some embodiments, the display is acathode ray tube (CRT). In some embodiments, the display is a liquidcrystal display (LCD). In further embodiments, the display is a thinfilm transistor liquid crystal display (TFT-LCD). In some embodiments,the display is an organic light emitting diode (OLED) display. Invarious further embodiments, on OLED display is a passive-matrix OLED(PMOLED) or active matrix OLED (AMOLED) display. In some embodiments,the processing device includes an input device to receive informationfrom a user. In some embodiments, the input device is a keyboard. Insome embodiments, the input device is a pointing device including, byway of non-limiting examples, a mouse, trackball, track pad, joystick,game controller, or stylus. In some embodiments, the input device is atouch screen or a multi-touch screen. In other embodiments, the inputdevice is a microphone to capture voice or other sound input. In otherembodiments, the input device is a video camera or other sensor tocapture motion or visual input. In still further embodiments, the inputdevice is a combination of devices such as those disclosed herein.

Referring to FIG. 4, in an exemplary platform 400, an exemplary system410 is programmed or otherwise configured to, for example, dynamicallyload data provider connector modules and/or request, procure, process,analyze, persist and/or provide one or more data records. In thisembodiment, the system 400 includes a processor 412 (also known as acentral processing unit (CPU) and “computer processor”), which can be asingle core or multi core processor, or a plurality of processors forparallel processing. System 410 also includes memory or memory location(e.g., random-access memory, read-only memory, flash memory), systemstorage 430 (e.g., hard disk), a communication interface (e.g., networkadapter) for communicating with one or more other systems, andperipheral devices, such as cache, other memory, data storage and/orelectronic display adapters. The memory, system storage 430, networkinterface and peripheral devices are in communication with the CPU 412through a communication bus, such as a motherboard. The system storage430 can be a data storage unit (or data repository) for storing data.System 410 can be operatively coupled to a computer network (“network”)with the aid of the communication interface. The network can be theInternet, an internet and/or extranet, or an intranet and/or extranetthat is in communication with the Internet. The network in some cases isa telecommunication and/or data network. The network can include one ormore computer servers, server clusters and/or distributed computingresources, providing, for example cloud computing. The network, in somecases with the aid of the system 410, can implement a peer-to-peernetwork, which may enable devices coupled to the device 501 to behave asa client or a server.

In some embodiments, the CPU 412 can execute a sequence ofmachine-readable instructions, which can be embodied in a program orsoftware. The instructions may be stored in a memory location, such asthe memory. The instructions can be directed to the CPU 412, which cansubsequently program or otherwise configure the CPU 412 to implementmethods of the present disclosure. The CPU 412 can be part of a circuit,such as an integrated circuit. One or more other components of thesystem 410 can be included in the circuit. In some cases, the circuit isan application specific integrated circuit (ASIC) or a fieldprogrammable gate array (FPGA).

In some embodiments, the system storage 430 can store files such asdrivers, libraries and saved programs. The system storage 430 can storeuser data, e.g., user preferences and user programs. The system 410 insome cases can include one or more additional data storage units thatare external, such as located on a remote server, remote server cluster,network attached storage, or the like, that is in communication throughan intranet or the Internet. In some embodiments, methods as describedherein can be implemented by way of machine (e.g., computer processor)executable code stored on an electronic storage location of the system410, such as, for example, on the memory or system storage 430. Themachine executable or machine readable code can be provided in the formof software. During use, the code can be executed by the CPU 412. Insome cases, the code can be retrieved from the system storage 430 andstored on the memory for ready access by the CPU 412. In somesituations, the system storage 430 can be precluded, andmachine-executable instructions are stored on memory. In someembodiments, the code is pre-compiled. In some embodiments, the code iscompiled during runtime. The code can be supplied in a programminglanguage that can be selected to enable the code to execute in aprecompiled or as-compiled fashion.

In some embodiments, the system 410 can include or be in communicationwith an electronic display 470. In some embodiments, the electronicdisplay 470 provides a user interface or GUI.

Non-Transitory Computer Readable Storage Medium

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include one or more non-transitory computer readablestorage media encoded with a program including instructions executableby the operating system of an optionally networked processing device. Infurther embodiments, a computer readable storage medium is a tangiblecomponent of a processing device. In still further embodiments, acomputer readable storage medium is optionally removable from aprocessing device. In some embodiments, a computer readable storagemedium includes, by way of non-limiting examples, CD-ROMs, DVDs, flashmemory devices, solid state memory, magnetic disk drives, magnetic tapedrives, optical disk drives, distributed computing systems includingcloud computing systems and services, and the like. In some cases, theprogram and instructions are permanently, substantially permanently,semi-permanently, or non-transitorily encoded on the media.

Computer Program

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include at least one computer program, or use of thesame. A computer program includes a sequence of instructions, executablein the processing device's CPU, written to perform one or more specifiedtasks. Computer readable instructions may be implemented as programmodules, such as functions, objects, Application Programming Interfaces(APIs), data structures, and the like, that perform particular tasks orimplement particular abstract data types. In light of the disclosureprovided herein, those of skill in the art will recognize that acomputer program may be written in various versions of variouslanguages. The functionality of the computer readable instructions maybe combined or distributed as desired in various environments. In someembodiments, a computer program comprises one sequence of instructions.In some embodiments, a computer program comprises a plurality ofsequences of instructions. In some embodiments, a computer program isprovided from one location. In other embodiments, a computer program isprovided from a plurality of locations. In various embodiments, acomputer program includes one or more software modules. In variousembodiments, a computer program includes, in part or in whole, one ormore web applications, one or more mobile applications, one or morestandalone applications, one or more web browser plug-ins, extensions,add-ins, or add-ons, or combinations thereof.

Web Application

In some embodiments, a computer program includes a web application. Inlight of the disclosure provided herein, those of skill in the art willrecognize that a web application, in various embodiments, utilizes oneor more software frameworks and one or more database systems. In someembodiments, a web application is created upon a software framework suchas Microsoft®.NET or Ruby on Rails (RoR). In some embodiments, a webapplication utilizes one or more database systems including, by way ofnon-limiting examples, relational, non-relational, object oriented,associative, and XML database systems. In further embodiments, suitablerelational database systems include, by way of non-limiting examples,Microsoft® SQL Server, mySQL™, and Oracle®. Those of skill in the artwill also recognize that a web application, in various embodiments, iswritten in one or more versions of one or more languages. A webapplication may be written in one or more markup languages, presentationdefinition languages, client side scripting languages, server-sidecoding languages, database query languages, or combinations thereof. Insome embodiments, a web application is written to some extent in amarkup language such as Hypertext Markup Language (HTML), ExtensibleHypertext Markup Language (XHTML), or eXtensible Markup Language OiML).In some embodiments, a web application is written to some extent in apresentation definition language such as Cascading Style Sheets (CSS).In some embodiments, a web application is written to some extent in aclient-side scripting language such as Asynchronous JavaScript and XML(AJAX), Flash® ActionScript, Javascript, or Silverlight®. In someembodiments, a web application is written to some extent in aserver-side coding language such as Active Server Pages(ASP),ColdFusion®, Perl, Java™, JavaServer Pages (JSP), Hypertext Preprocessor(PHP), Python™, Ruby, Tcl, Smalltalk, WebDNA®, or Groovy. In someembodiments, a web application is written to some extent in a databasequery language such as Structured Query Language (SQL). In someembodiments, a web application integrates enterprise server productssuch as IBM® Lotus Domino®. In some embodiments, a web applicationincludes a media player element. In various further embodiments, a mediaplayer element utilizes one or more of many suitable multimediatechnologies including, by way of nonlimiting examples, Adobe® Flash®,HTML 5, Apple® QuickTime®, Microsoft® Silverlight®, Java™, and Unity®.

Mobile Application

In some embodiments, a computer program includes a mobile applicationprovided to a mobile processing device. In some embodiments, the mobileapplication is provided to a mobile processing device at the time it ismanufactured. In other embodiments, the mobile application is providedto a mobile processing device via the computer network described herein.

In view of the disclosure provided herein, a mobile application iscreated by techniques known to those of skill in the art using hardware,languages, and development environments known to the art. Those of skillin the art will recognize that mobile applications are written inseveral languages. Suitable programming languages include, by way ofnon-limiting examples, C, C++, C#, Objective-C, Java™, Javascript,Pascal, Object Pascal, Python™, Ruby, VB .NET, WML, and XHTML/HTML withor without CSS, or combinations thereof.

Suitable mobile application development environments are available fromseveral sources. Commercially available development environmentsinclude, by way of non-limiting examples, AirplaySDK, alcheMo,Appcelerator®, Celsius, Bedrock, Flash Lite, .NET Compact Framework,Rhomobile, and WorkLight Mobile Platform. Other development environmentsare available without cost including, by way of non-limiting examples,Lazarus, Mobi-Flex, MoSync, and Phonegap. Also, mobile devicemanufacturers distribute software developer kits including, by way ofnon-limiting examples, iPhone and iPad (iOS) SDK, Android™ SDK,BlackBerry® SDK, BREW SDK, Palm® OS SDK, Symbian SDK, webOS SDK, andWindows® Mobile SDK.

Those of skill in the art will recognize that several commercial forumsare available for distribution of mobile applications including, by wayof non-limiting examples, Apple® App Store, Google® Play, Chrome WebStore, BlackBerry® App World, App Store for Palm devices, App Catalogfor webOS, Windows® Marketplace for Mobile, Ovi Store for Nokia®devices, Samsung® Apps, and Nintendo® DSi Shop.

Software Modules

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include software, server, and/or database modules, oruse of the same. In view of the disclosure provided herein, softwaremodules are created by techniques known to those of skill in the artusing machines, software, and languages known to the art. The softwaremodules disclosed herein are implemented in a multitude of ways. Invarious embodiments, a software module comprises a file, a section ofcode, a programming object, a programming structure, or combinationsthereof. In further various embodiments, a software module comprises aplurality of files, a plurality of sections of code, a plurality ofprogramming objects, a plurality of programming structures, orcombinations thereof. In various embodiments, the one or more softwaremodules comprise, by way of nonlimiting examples, a web application, amobile application, and a standalone application. In some embodiments,software modules are in one computer program or application. In otherembodiments, software modules are in more than one computer program orapplication. In some embodiments, software modules are hosted on onemachine. In other embodiments, software modules are hosted on more thanone machine. In further embodiments, software modules are hosted oncloud computing platforms. In some embodiments, software modules arehosted on one or more machines in one location. In other embodiments,software modules are hosted on one or more machines in more than onelocation.

Databases

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include one or more databases, or use of the same. Inview of the disclosure provided herein, those of skill in the art willrecognize that many databases are suitable for storage and retrieval ofdata, such as digital media collectibles described herein. In variousembodiments, suitable databases include, by way of non-limitingexamples, relational databases, nonrelational databases, object orienteddatabases, object databases, entity-relationship model databases,associative databases, and XML databases. In some embodiments, adatabase is web-based. In still further embodiments, a database is cloudcomputing-based. In other embodiments, a database is based on one ormore local computer storage devices.

Various methods have been described herein to generate, maintain, anddisplay 3D digital collectibles, including methods using exemplarysteps. It may be understood that more or less steps may be included, andthat the illustrated steps are merely non-limiting examples. Nor is theorder in which the steps are presented/described indicative of any setor requisite order that must be followed. It should be appreciated thatvarious prompts, cues, buttons, and/or other graphical/visualinteractive elements may be presented to the user together with one ormore of these steps. _Steps depicted herein may correspond toinstructions stored in computer readable storage medium which can beexecuted by one or more processors of computing components describedherein, for example as part of computing components disclosed herein.

While the invention has been particularly shown and described withreference to exemplary embodiments thereof, the invention is not limitedto these embodiments. It will be understood by those of ordinary skillin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the invention as definedby the following claims.

1. A computer system for generating and displaying a 3D virtual displayelement on a graphical user interface, the display element representinga digital collectible comprising content including at least one digitalmedia file, data relating to the digital media file, and scarcity databased on a predetermined configuration, comprising: at least oneprocessor; a computer-readable storage medium having instructions storedthereon which are executable by the at least one processor and which,when executed, cause the computing system to: configure a 3D virtualdisplay element comprising n-surfaces and a specification of content todisplay on the surfaces; generate and display the 3D virtual displayelement, including a display of the digital media file when arepresentation of a first surface of the 3D virtual display element isforward facing; a display of data relating to the digital media filewhen a second surface of the 3D virtual display element is forwardfacing, and a display of an indication of scarcity based on the scarcitydata.
 2. The system of claim 1, wherein the display of an indication ofscarcity comprises a graphical visual indicator on or adjacent to afirst surface of the n-surfaces of the 3D virtual display element. 3.The system of claim 1, wherein the scarcity data comprises: apredetermined number of instances of the 3D digital collectible in afirst batch, where the predetermined number may be guaranteed not toincrease; a unique serial number comprising a unique number between 1-n,where n is the predetermined number of instances of the 3D digitalcollectible in the first batch; or a combination of the predeterminednumber of instances and unique serial number.
 4. The system of claim 1,further comprising an administrative module configured for specifyingrules and metadata relating to an event, the instructions being furtherconfigured to: create a data structure in the storage medium comprisingan event input via the administrative module, the data structurecomprising an event identifier, content related to the event, rulesspecifying the display characteristics of the 3D virtual displayelement, including the number of n sides for the 3D virtual displayelement, and a designation of the content to be rendered on various onesof the n sides of the n-sided 3D shape; and specify a number ofinstances of the digital collectible to be created and storing thenumber of instances of the digital collectible as scarcity data, theinstructions further comprising rules for classifying a scarcity levelof the digital collectible based on the number of instances of thedigital collectable and rules for generating the indication of scarcitybased on the scarcity level so as to visually distinguish a digitalcollectible of a first scarcity level from a digital collectible of asecond scarcity level.
 5. A computer system for generating anddisplaying a 3D virtual display element on a graphical user interface,the display element representing a digital collectible comprisingcontent including at least one digital media file, data relating to thedigital media file, and scarcity data based on a predeterminedconfiguration, comprising: at least one processor; a computer-readablestorage medium having instructions stored thereon which are executableby the at least one processor and which, when executed, cause thecomputing system to: configure a 3D virtual display element comprisingan n-sided 3D shape, an overlay display element arranged at a firstdistance from the n-sided 3D shape, and a specification of content todisplay on at least one of the n sides of the n-sided 3D shape and theoverlay display element; generate and display the 3D virtual displayelement, including a display of the digital media file when arepresentation of a first side of the n-sided 3D shape is forwardfacing, a display of content relating to the digital media file when asecond side of the n-sided 3D shape is forward facing; the overlaydisplay element adjacent to and overlaying at least a portion of thefirst side of the n-sided 3D shape; and a display of an indication ofscarcity based on the scarcity data.
 6. The system of claim 5, whereinthe display of an indication of scarcity comprises a graphical visualindicator on or adjacent to a first surface of the n-surfaces of the 3Dvirtual display element.
 7. The system of claim 5, wherein the scarcitydata comprises: a predetermined number of instances of the 3D digitalcollectible in a first batch, where the predetermined number may beguaranteed not to increase; a unique serial number comprising a uniquenumber between 1-n, where n is the predetermined number of instances ofthe 3D digital collectible in the first batch; or a combination of thepredetermined number of instances and unique serial number.
 8. Thesystem of claim 5, further comprising an administrative moduleconfigured for specifying rules and metadata relating to an event, theinstructions being further configured to: create a data structure in thestorage medium comprising an event input via the administrative module,the data structure comprising an event identifier, content related tothe event, rules specifying the display characteristics of the 3Dvirtual display element, including the number of n sides for the 3Dvirtual display element, characteristics of the overlay display element,and a designation of the content to be rendered on various ones of the nsides of the n-sided 3D shape and the overlay display element; andspecify a number of instances of the digital collectible to be createdand storing the number of instances of the digital collectible asscarcity data, the instructions further comprising rules for classifyinga scarcity level of the digital collectible based on the number ofinstances of the digital collectable and rules for generating theindication of scarcity based on the scarcity level so as to visuallydistinguish a digital collectible of a first scarcity level from adigital collectible of a second scarcity level.
 9. A computer system forgenerating and displaying a 3D virtual display element on a graphicaluser interface, the display element representing a digital collectiblecomprising content including at least one digital media file, datarelating to the digital media file, and scarcity data based on apredetermined configuration, comprising: at least one processor; acomputer-readable storage medium having instructions stored thereonwhich are executable by the at least one processor and which, whenexecuted, cause the computing system to: configure a 3D virtual displayelement comprising an n-sided 3D shape, an overlay display elementarranged at a first distance from the n-sided 3D shape, a surroundingstructure display element, said surrounding structure display elementcomprising a framework forming at least part of an n-sided 3D frameworkshape conforming to at least part of the n-sided 3D shape of the 3Dvirtual display element, and a specification of content to display on atleast one of the n sides of the n-sided 3D shape and the overlay displayelement; generate and display the 3D virtual display element, includinga display of the digital media file when a representation of a firstside of the n-sided 3D shape is forward facing, a display of contentrelating to the digital media file when a second side of the n-sided 3Dshape is forward facing; the overlay display element adjacent to andoverlaying at least a portion of the first side of the n-sided 3D shape;and a graphical visual indicator on the surrounding structure displayelement indicating a level of scarcity based on the scarcity data. 10.The system of claim 9, wherein the scarcity data comprises: apredetermined number of instances of the 3D digital collectible in afirst batch, where the predetermined number may be guaranteed not toincrease; a unique serial number comprising a unique number between 1-n,where n is the predetermined number of instances of the 3D digitalcollectible in the first batch; or a combination of the predeterminednumber of instances and unique serial number.
 11. The system of claim 9,further comprising an administrative module configured for specifyingrules and metadata relating to an event, the instructions being furtherconfigured to: create a data structure in the storage medium comprisingan event input via the administrative module, the data structurecomprising an event identifier, content related to the event, rulesspecifying the display characteristics of the 3D virtual displayelement, including the number of n sides for the 3D virtual displayelement, characteristics of the overlay display element, characteristicsof the surrounding structure display element, and a designation of thecontent to be rendered on various ones of the n sides of the n-sided 3Dshape and the overlay display element, and the graphical visualindicator on the surrounding structure display element; and specify anumber of instances of the digital collectible to be created and storingthe number of instances of the digital collectible as scarcity data, theinstructions further comprising rules for classifying a scarcity levelof the digital collectible based on the number of instances of thedigital collectable and rules for generating the graphical visualindicator based on the scarcity level so as to visually distinguish adigital collectible of a first scarcity level from a digital collectibleof a second scarcity level.